Building the RTXC library or any of the demonstration applications requires the compilation and/or assembly of the source code. RTXC switch options are used during the build process to modify the configuration of your RTXC application. There are two basic types of RTXC switch options; structural specifications and object/services specification. These switch options are found in the RTXC options files, RTXCOPTS.H, RTXCOPTS.INC, AOPTIONS.H and AOPTIONS.INC, KOPTIONS.H and KOPTIONS.INC. The generation utility program, RTXCgen, will generate AOPTIONS.H, AOPTIONS.INC, KOPTIONS.H and KOPTIONS.INC.

* Note: The .INC extension on the above files is an assembler specific extension for an assembly include or header file. Your assembler might use a different extension.

The most common binding options are contained in the AOPTIONS and KOPTIONS files that are easily generated using RTXCgen. Refer to RTXCgenBindingOptions.

Options listed below may be changed by editing the RTXCOPTS.H and RTXCOPTS.INC files. These options rarely need to be changed. The user may determine what is right for his application.

1 RTXC Binding Specific Structural Specification in RTXCOPTS.H

There are several conditional compilation switches found in RTXCOPTS.H through which you may exercise complete control over your configuration of RTXC. These switches are set or cleared by the use of the two C language preprocessor directives, #define and #undef. If you want to include a particular item in the RTXC configuration, select it by using a #define with the switch name. Conversely, if you want to exclude an item, #undef it. Some of these switches have assembly language counterparts in RTXCOPTS.INC.

RTXC is distributed with a default selection of most switches. Some of these are particular to the processor and are not likely to change. Others can be set or cleared to suit your needs.

These configuration options are considered binding specific options. The binding options listed below are specific to this binding (compiler tool set and processor specific) of RTXC.

There are several specifications of switch conditions, which work towards determining the exact configuration of RTXC. Among these are the language interface to RTXC and the kernel call model. These switches are explained below.

1.1 HAS_RAM_VECTORS

This option determines whether the vectors are located in RAM or ROM.

1.2 SET_MODESTACKS

This option selects whether each mode stack (SVC, IRQ, FIQ) must be initialized by the application upon entry into the application. Normally, this is done by the Angel ROM monitor. When using a standalone system such as EmbeddedICE or Multi-ICE, you must define the mode stacks.

2 RTXC Binding Specific Structural Specification in RTXCOPTS.INC

Please note, a number of the switches found in RTXCOPTS.H have corresponding assembler switches in RTXCOPTS.INC. The assembly switch is an equate which is either set to {TRUE} or {FALSE}. For convenience those switches which exist in the RTXCOPTS.H and RTXCOPTS.INC are denoted with "** CONFIG **" preceding the switch name in the switch description.

2.1 HAS_RAM_VECTORS

See section 1.1 above

2.2 SET_MODESTACKS

See section 1.2 above

2.3 angel_SWI_vector

This constant defines the SWI vector used by the Angel ROM Monitor to get to SVC mode.

2.4 SWI_Angel

This constant defines the SWI number used by the Angel ROM Monitor to get to SVC mode.